Skip to content

Conversation

@fw-immunant
Copy link
Contributor

@fw-immunant fw-immunant commented Jan 8, 2026

Fixes #315. That said, this is atop #595 which causes problems as I haven't finished debugging the tracer's hangs.

None => None,
Some(overlap) => Some((
Self::from_bounds(self.start, overlap.start),
Self::from_bounds(self.end(), overlap.end()),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

won't this always return None, if self.end() >= overlap.end() (given the ordering of the args), and is that a problem?

struct memory_map *load_initial_memory_map(pid_t pid) {
char *filename = NULL;
asprintf(&filename, "/proc/%d/maps", pid);
FILE *maps_file = fopen(filename, "r");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this ever closed?

@oinoom
Copy link
Contributor

oinoom commented Jan 13, 2026

Maybe not directly related to this PR, but I was looking through the track memory map given your hang issues, and noted that I didn't see handling in the syscall-exit path for WAIT_GROUP_STOP, WAIT_SIGSEGV, WAIT_SIGNALED, WAIT_CONT, and WAIT_PTRACE_FORK. Hopefully this helps. I wonder about the last one and if that's the one that's causing the hangs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Memory map does not track initial mappings

3 participants